- Add MongoDbRateLimitService class implementing RateLimitService interface
- Use MongoDB TTL index for efficient automatic purging of old records
- Implement checkRequest method with counting and limiting logic
- Add error handling and logging

- Add RateLimitService interface
- Implement MongoDbRateLimitService
- Integrate RateLimitService into AppDependencies
- Update dependency initialization and disposal

- Add TTL index for automatic document expiration in rate limit attempts collection
- Add key index for faster lookups in rate limit attempts collection
- Implement indexing in the DatabaseSeedingService

- Add rateLimiter middleware function to enforce rate limiting on routes
- Include ipKeyExtractor for IP-based rate limiting
- Implement _getIpAddress to extract client's IP address from request
- Add RateLimitService for tracking and limiting requests

- Add special case for ForbiddenException containing 'too many requests'
- Map to 429 Too Many Requests status code for rate limiting errors

- Import RateLimitService from services package
- Add RateLimitService to the middleware chain using provider

- Implement rate limiting middleware for the /request-code endpoint
- Allow up to 3 requests per IP address every 24 hours
- Use ipKeyExtractor for rate limiting key generation
- Refactor handler logic to include rate limiting

- Add new environment variables for rate limiting configuration
- Include settings for /auth/request-code and /data API endpoints
- Specify limit and time window for each endpoint

- Introduce new environment variables for request-code and data API rate limiting
- Implement getters for rate limit parameters with default values
- Add documentation for new configuration options

…e limiting

- Rename request-code.dart to index.dart for better modularity
- Implement rate limiting middleware directly in the handler
- Improve code structure and prepare for additional endpoint implementations

- Implement rate limiting specifically for the `/api/v1/auth/request-code` endpoint
- Use custom rate limit configuration from EnvironmentConfig
- Apply rateLimiter middleware with ipKeyExtractor for key generation

- Reduced the whitespace between blocks in the `onRequest` function
- Improved code readability and formatting without changing functionality

- Add new permission 'rate_limiting.bypass' to permissions.dart
- Grant this new permission to dashboard publisher and admin roles in role_permissions.dart

- Add rate limiting middleware for /api/v1/data routes
- Implement bypass permission for rate limiting
- Configure rate limit using environment variables
- Update middleware documentation and comments

- Removed detailed documentation from _middleware.dart file
- Kept existing middleware functions intact

- Add explanation for optional rate limiting configuration
- Provide default values and units for rate limit settings
- Improve clarity on purpose and usage of rate limiting options

- Add information about built-in API rate limiting to README.md
- Highlight protection against abuse and denial-of-service attacks
- Mention configurable, user-aware limits and trusted role bypass
- Emphasize stability and cost prevention benefits

- Change default JWT expiry hours from 1 hour to 720 hours (1 month)
- Modify the fallback value in int.tryParse from '1' to '720'
- This change affects the jwtExpiryDuration getter in EnvironmentConfig class

- Change JWT_EXPIRY_HOURS default from 1 hour to 720 hours (1 month)
- Update ADMIN OVERRIDE to REQUIRED for the single administrator account setting
- Clarify optional rate limit configuration for API endpoints